Wireless chat automatic status signaling

ABSTRACT

A technique and apparatus to provide status tracking of presence and/or location of wireless devices to requesting entities inside and/or outside a particular wireless system. Presence and/or location information is provided to entities outside a particular servicing wireless network via mechanisms of call processing components of a mobile network and standard mechanisms available to any appropriately conforming MSC element. In one embodiment, a wireless chat automatic status tracking system utilizes a change in mobile registration status to automatically forward or copy a registration notification (REGNOT) message to an external IP application, to notify a chat group system outside the wireless network of current status information activity regarding a relevant device. Change in mobile registration is communicated via a suitable signaling link between a HLR and the chat group system. REGNOT messages are pushed over TCP/IP connections to external applications to automatically notify the external system of a particular user&#39;s location.

This application is a continuation of U.S. application Ser. No.12/929,790, entitled “Wireless Chat Automatic Status Signaling” to Unget al., filed Feb. 16, 2011; which in turn is a continuation of U.S.application Ser. No. 12/379,448, entitled “Wireless Chat AutomaticStatus Signaling” to Ung et al., filed on Feb. 23, 2009, now U.S. Pat.No. 7,894,797; which in turn is a continuation of No. 09/814,363,entitled “Wireless Chat Automatic Status Tracking” to Ung et al., filedon Mar. 23, 2001, now U.S. Pat. No. 7,522,911; which in claims priorityfrom Provisional Application No. 60/196,104, entitled “Mobile ActivityStatus Tracker” to Wallace et al., filed on Apr. 11, 2000; and from U.S.Provisional Application No. 60/196,099, entitled “Wireless Chat StatusTracking” to Ung et al., filed on Apr. 11, 2000; and is a continuationof U.S. application Ser. No. 09/576,022, entitled “Mobile ActivityStatus Tracker” to Wallace et al., filed on May 23, 2000, now U.S. Pat.No. 7,110,773, the entirety of all of which are expressly incorporatedherein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates generally to wireless carriers, Internet serviceproviders (ISPs), information content delivery services/providers,portal sites for mobile-terminated hosting of chat groups, and/orInternet chat session hosts. More particularly, it relates to thegateway perspective of mobile device functions such as ANSI-41 automaticregistration, real-time Internet message billing, real-time wirelessmessage billing, messaging in general, wireless chat, and/or Internetchat.

2. Background of Related Art

The present invention relates to improvements to mobile wirelesssystems, which currently include mobility management, IS-41 mobilitymanagement, and/or registration systems, to support, e.g., Internetchat, ICQ, etc.

Up to this point, in a Wireless & Internet chat group system, a chatmember must manually notify the system when he/she desires to go on-lineor off-line. This invention enables a wireless carrier and/or Internetservice provider to introduce a Wireless Intelligent Network (WIN)service that allows a chat room or session system to be automaticallynotified when the subscriber is on-line or off-line. This will allow,for example, the chat system to continually and automatically notify thesubscribers of the chat group or a “buddy list” about a participant'sstatus in a chat room/session at any time. This WIN service will beapplicable to both prepaid and postpaid IS-41 networks.

Currently no system is known to provide such WIN service for wirelessdevices. Existing systems allow the landline internet subscriber toautomatically notify the chat group when the subscriber goes on-line oroff-line.

Existing technologies have not addressed the concept of automaticnotification for wireless chat participants. Without this feature,members in the chat group are not aware of the member's actual status.The wireless participants have to remember to notify the chat group orbuddies of his/her availability.

As is known, presence information and location information regarding aparticular wireless device is recorded in a Home Location Register forthe relevant wireless network.

FIG. 10 shows a conventional stand-alone Home Location Register (SHLR)architecture and message flow of a Mobile Registration Notificationmessage (REGNOT).

In FIG. 10, a first wireless network 1060 includes a mobile switchingcenter MSC 1010 and a stand-alone Home Location Register (SHLR) 1040.The SHLR 1040 and the MSC 1010 communicate over the cellular telephonynetwork (and perhaps the PSTN when calls are connected to a land-lineswitch or calls need to be delivered via a trunk line that routesthrough a PSTN) via one or more switching transfer points (STPs) 1030.The protocol used for communication is IS-41 or GSM-MAP over signalingsystem No. 7 (SS7).

The service provider is typically given maintenance and configurationproprietary access to the database stored in the SHLR using anOperations and Maintenance Processor (OMP) and provisioning terminalconsole 1050, which may communicate with the SHLR using a point-to-pointlink, e.g., an X.25 link, an RS-232 link, or a TCP/IP link.Communications from the OMP 1050 typically relate to maintenance andconfiguration only, and do not relate to operational functions of therelevant wireless network.

A second wireless network 1070 servicing another wireless device 1090includes another MSC 1020, and utilizes one or more STPs 1030 in the SS7network.

In the given scenario, assume that the wireless device 1090 incommunication with the second wireless network 1070 is serviced by theservice provider of the first wireless network 1060. Thus, presence andlocation information regarding the second wireless device 1090 is storedand updated in the SHLR 1040 corresponding to its servicing network.

To communicate presence and location information to the ‘home’ registerof the second wireless device 1090, a MOBILE REGISTRATION message (1.)is sent in accordance with Signaling System #7 (SS7) standards usingIS-41C protocol messages through the second wireless network 1070 to theMSC 1020 of the second wireless network 1070. The ‘presence’ of awireless device relates to the wireless device being powered ON andreachable in the relevant wireless network.

The MSC 1020 forwards the MOBILE REGISTRATION message (1.) upon receiptto the STP 1030 as an IS-41 REGISTRATION NOTIFICATION (REGNOT) message(2.).

The STP 1030 forwards the REGNOT message (3.) to the appropriate SHLR1040 servicing that particular wireless device 1090.

In this way, the Home Location Register of a particular wireless device1040 is provided with presence and location information regarding thewhereabouts and registration activity of a particular subscriber (e.g.,wireless device 1090).

FIG. 10 relates to a Home Location Register which is installed as aseparate network element. Using a SHLR 1040 as shown in FIG. 10, theSHLR 1040 must communicate with the associated MSC 1010 using SS7signaling through the STP 1030. Presence and location information isupdated in a subscriber's Home Location Register in a similar mannerwhen the Home Location Register is integrated onto a common platformwith the MSC element. This configuration is known as an integrated HomeLocation Register (I-HLR).

FIG. 11 shows a conventional integrated Home Location Register (I-HLR)architecture and message flow of a Mobile Registration Notificationmessage (REGNOT) allowing proprietary communications between elementssuch as the MSC and I-HLR operating on a common platform.

In particular, as shown in FIG. 11, a MOBILE REGISTRATION message (1.)is sent to the MSC 1020 providing access to the roaming wireless device1090, and the MSC 1020 forwards the REGNOT message (2.) to the relevantSTPs 1030 as shown in FIG. 10. However, instead of forwarding the REGNOTmessage (3.) to the SHLR 1040 as shown in FIG. 10, the REGNOT message(3.) in FIG. 11 is forwarded to the common platform including both theMSC 1110 and the I-HLR 1140. The MSC 1110 and I-HLR 1140 may communicatewith one another using any desired proprietary communications protocol,without need to conform to the SS7 signaling protocol at that point.Nevertheless, the I-HLR 1140 is updated with presence and locationinformation regarding the roaming wireless device 1090.

In the conventional scenario, presence and location information isrestricted to use by the ‘home’ service provider of a particularwireless device. Using conventional signaling protocols, other wirelessnetworks are not provided with presence and location informationregarding wireless devices other than those which subscribe to itsservices. The presence and location information is conventional usedonly by the home service provider for routing of call information (e.g.,establishing a voice connection to a mobile wireless device).

Accordingly, there is a need for providing presence and locationinformation to entities other than just those servicing a particularwireless device, thus enabling a new host of network services andapplications.

SUMMARY OF THE INVENTION

In accordance with the principles of the present invention, in a shortmessage service center, a module for permitting automatic statustracking of a wireless chat participant by an application external to aservice provider including said short message service center, a REGNOTand/or MSInactive handler comprises a registration notification and/oran MS inactivity messages receiver, and a registration/inactive messageforwarder to forward a registration notification and/or MS inactivitymessage received by a mobile switching center over an Internetconnection.

A method for automatically notifying an external chat server of apresence of a chat session participant in accordance with another aspectof the present invention comprises receiving an IS-41 conformingregistration notification and MS inactive messages from one of a mobiletelephony network, mobile switching center, I-HLR, and S-HLR or STP, andautomatically forwarding the IS-41 conforming registration notificationand MS inactive messages over an Internet connection to an external chatserver.

BRIEF DESCRIPTION OF THE DRAWINGS

Features and advantages of the present invention will become apparent tothose skilled in the art from the following description with referenceto the drawings. Note that for simplicity of explanation, only a REGNOTmessage is shown in the figures. However, an MS inactivity (MSInactive)message may be conveyed in the same way as the REGNOT message. In thedrawings:

FIG. 1 shows an exemplary architecture and information flow of a mobileactivity status tracker (MAST) system, in accordance with the principlesof the present invention.

FIG. 2 is a more detailed architecture and information flow of anembodiment of a MAST system corresponding to a stand-alone Home LocationRegister (SHLR) including a registration notification forwardingmechanism utilizing message flows in conformance with SS7 standards andIS-41 standards, in accordance with the principles of the presentinvention.

FIG. 2A shows a block diagram of the basic elements of an exemplary MASTsystem shown in FIG. 2.

FIG. 3 is a detailed architecture and information flow of an embodimentof a MAST system corresponding to an integrated Home Location Register(I-HLR) including a registration notification forwarding mechanismintegrated with a mobile switching center (MSC) on a common platform,utilizing message flows in conformance with SS7 standards and IS-41standards, in accordance with the principles of the present invention.

FIG. 4 is a detailed architecture and information flow of an embodimentof a MAST system corresponding to a stand-alone Home Location Register(SHLR) including a Registration Notification copy function in asignaling transfer point (STP) and a TCP/IP connection (or SS7connection) to the MAST application, particularly useful in wirelessnetworks having HLRs which do not include a registration notificationforwarding mechanism, in accordance with the principles of the presentinvention.

FIG. 5A is a simplified depiction of relevant parameters of a MobileRegistration Notification (REGNOT) message in conformance with SS7 andIS-41 standards utilized for determination of location information in aMAST system, in accordance with the principles of the present invention.

FIG. 5B is a detailed depiction of all conventional parameters of aREGNOT message.

FIG. 6 is a simplified depiction of relevant parameters of a MobileSubscriber Inactive message in conformance with SS7 and IS-41 standardsutilized for determination of inactive presence information in a MASTsystem, in accordance with the principles of the present invention.

FIG. 6B is a detailed description of the otherwise conventionalMSInactive message parameters.

FIG. 7A is a simplified depiction of relevant parameters such aslocation in an exemplary Internet Protocol (IP) message sent from theMAST system to an application server (e.g., a Chat Server) via theInternet, in accordance with the principles of the present invention.

FIG. 7B is a simplified depiction of relevant parameters in anotherexemplary IP message such as a log of past presence and locationinformation for a particular wireless device sent from the MAST systemto an application server (e.g., a law enforcement authority) via theInternet, in accordance with the principles of the present invention.

FIG. 8 shows an exemplary Mobile Station Identity (MSID) ordered table,in accordance with the principles of the present invention.

FIG. 9 shows an exemplary process by which the parsed message portionsare processed.

FIG. 10 shows a conventional stand-alone Home Location Register (SHLR)architecture and message flow of a Mobile Registration Notificationmessage (REGNOT).

FIG. 11 shows a conventional integrated Home Location Register (I-HLR)architecture and message flow of a Mobile Registration Notificationmessage (REGNOT) allowing proprietary communications between elementssuch as the MSC and I-HLR operating on a common platform.

FIG. 12 shows an exemplary service implementation showing wireless chatstatus tracking providing an automatic on-line or off-line notificationin a chat scenario using techniques and apparatus in accordance with theprinciples of the present invention.

FIG. 13 shows a block diagram of the SMSC shown in FIG. 12, including aREGNOT/MSInactive message receiver, a REGNOT/MSInactive forwarder, andan optional REGNOT/MSInactive copier, in accordance with the principlesof the present invention.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

The present invention relates to a technique and apparatus to providestatus tracking of presence and/or location of a mobile, wireless deviceto a requesting entity even outside of a particular wireless system.This allows wireless service providers the ability to monitor and logchanges in the status of mobile stations within and/or outside theirnetworks enabling the development of multiple applications and networkservices. Embodiments are disclosed wherein presence and/or locationinformation is provided to entities outside of a particular servicingwireless network using the mechanisms of call processing components of amobile network (e.g., call setup procedures), and using standardmechanisms currently available to any appropriately conforming MobileSwitching Center (MSC) element. An embodiment implementing a wirelesschat automatic status tracking system and method is also disclosed.

Mobile presence and location are key concepts for location-basedservices and applications which require knowledge of mobilestation/subscriber availability. Currently, conventional systems do notprovide such wireless intelligent network (WIN) service for wirelessdevices.

It is important to note that existing systems and techniques have beenconventionally located outside of a wireless network. As such, theexisting systems have not been privy to, nor had the need to be privyto, triggers needed to obtain true mobile presence or locationinformation.

Mobile Activity Status Tracker (MAST)

One series of disclosed embodiments relate to a software applicationpackage which tracks and reports status and activity of mobile wirelessdevices in a wireless network using mobile registration message,inactivity message forwarding, and/or mobile automatic notification ofsubscriber status to TCP/IP entities. This embodiment of a mobileactivity status tracker is referred to herein as a Mobile ActivityStatus Tracker (MAST).

In accordance with the principles of the present invention, statuschanges that are recorded are sent via TCP/IP communications to otherservice provider-specific applications. The MAST system duplicates thesame or similar information of a corresponding HLR, but is available asan external database entity which functions and communications are notrestricted by SS7 standards.

Tracking in accordance with the principles of the present inventionutilizes registration/de-registration activity of mobile stations.Utilizing status changes for a particular mobile station, key events canbe noted regarding presence and/or location of the particular mobilestation.

The MAST application offers entities (e.g., Internet and others) outsideof a wireless infrastructure the ability to receive presence and/orlocation information regarding a particular mobile station to networkentities outside of that which is servicing a particular wirelessdevice. As disclosed, the MAST application has the ability to pullpresence and/or location information or to push presence and/or locationinformation to a requesting entity as desired.

Certain capabilities such as registration notification forwardingmechanisms/Registration Notification Forward Message and SMPP clientwhich are basic to this application, are described in detail in twopending U.S. applications by the same Assignee as the present case. Inparticular, an exemplary SMSC is described in co-pending and co-ownedU.S. application Ser. No. 09/322,929, entitled “Short Message ServiceNotification Between Multiple Short Message Service Centers”, filed Jun.1, 1999, by Timothy J. Lorello and Reuben D. Hart, the entirety of whichis explicitly incorporated herein by reference. Moreover, an exemplaryPrepaid functionality and architecture is described in co-pending andco-owned U.S. application Ser. No. 09/533,805, entitled “Prepaid CallManagement In Intelligent Network”, filed Mar. 23, 2000, by ElizabethCountryman, Timothy J. Lorello, Mark Titus, and Dara Ung, the entiretyof which is explicitly incorporated herein by reference.

The Mobile Activity Status Tracker (MAST) is a Service PackageApplication (SPA) that allows wireless service providers to monitor andlog changes in the status of mobile stations within their networks. Thestatus changes that are recorded are sent via TCP/IP to other serversfor service provider-specific applications. The tracking involves theregistration/de-registration activity and location of the mobilestations. The tracking need not track call-specific information, e.g.,called telephone numbers or information regarding conversationssustained by the tracked wireless subscribers.

Some disclosed embodiments relate to the use of a Home Location Register(HLR) which is integrated with a Mobile Switching Center (MSC) on acommon platform, referred to herein as Integrated Home LocationRegisters (I-HLRs) commercially available from LUCENT TECHNOLOGIES INC.in Murray Hill, N.J. Other embodiments relate to the use of astand-alone HLR separate from the MSC platform, referred to herein asStand alone HLR's (S-HLR). All types of HLRs are collectively referredto herein as an HLR.

The disclosed MAST SPA is implemented on an Advantage Service ControlPoint (SCP) Wireless Intelligent Network Platform, commerciallyavailable from LUCENT TECHNOLOGIES INC. The SCP provides the requiredANSI SS7 and TCP/IP protocol support and Service Circuit Handlers (SCH)for the MAST SPA.

In accordance with the principles of the present invention, the MAST SPAreceives mobile activity notifications from an HLR, and forwardsselected parameters upon request or configuration to servers external tothe wireless network over a TCP/IP communication link (e.g., over theInternet or over an Intranet).

FIG. 1 shows an exemplary architecture and information flow of a mobileactivity status tracker (MAST) system, in accordance with the principlesof the present invention.

In particular, as shown in FIG. 1, the operation of the exemplary MASTSPA includes the following exemplary steps:

(1) The handset exchanges activity information with the I-HLR, which inturn sends the Mobile Station Identity (MSID) of the mobile station anda set of relevant parameters to the MAST SPA in a registrationnotification forwarding mechanism message.

(2) The MAST SPA creates a temporary record for that mobile handsetbased on the MSID. The MAST performs a lookup in a database of existingrecords, using the MSID as a key. If there is no record for the MSID,then the temporary record is stored in the database. If there is arecord for the same MSID, the MAST compares the temporary record withthat found in the database to determine any changes in the activitystatus of the mobile station (or any other relevant parameters). If theactivity status is the same (i.e., unchanged), the MAST overwrites theold record with the new one. On the other hand, if the activity statushas changed, the activity status of the relevant mobile wireless devicewill be Notified or Forwarded to one or more application servers havingaccess to the Internet using an appropriate TCP/IP interface andappropriate IP addresses (or other suitable protocol and communicationpath, e.g., SS7). To this end, the MAST SPA will forward a set ofselected parameters (e.g., a subset of the parameters available in thetemporary record) to one or more requesting or pre-configuredapplications servers using corresponding Internet Protocol (IP)addresses. The MAST then replaces the existing, older record with thenew, updated record.

Preferably, the MAST resides on an SCP and accepts copies of IS-41Registration Notification and MSInactive messages from the HLR(s).

FIG. 2 is a more detailed architecture and information flow of anembodiment of a MAST system 200 corresponding to a stand-alone HomeLocation Register (SHLR) 240 including a registration notificationforwarding mechanism utilizing message flows in conformance with SS7standards and IS-41 standards, in accordance with the principles of thepresent invention.

In particular, FIG. 2 shows a MAST system 200 implemented by aparticular service provider corresponding to a first wireless network260. The first wireless network 260 also includes an MSC 1010, and aSHLR 240.

A second wireless network 1070 is shown for completeness andperspective. The second wireless network 1070 includes an MSC 1020, andservices a wireless device 1090.

The MAST 200 provides presence and/or location information regarding anyor all subscriber's of the first wireless network to external entities,without the need to change current communication standards, e.g.,utilizing otherwise conventional SS7 and IS-41 communication messages.

The MAST 200 includes information similar to that contained in the SHLR,e.g., relating to the presence and/or location of serviced wirelessdevices. However, in accordance with the principles of the presentinvention, the MAST 200 may include additional information, and/orlogged information over time with respect to each individual subscriber.The MAST 200 may be implemented on a same type platform as thatimplementing the SHLR 240, e.g., an SCP commercially available fromLUCENT TECHNOLOGIES INC.

FIG. 2A shows a block diagram of the basic elements of an exemplary MASTsystem 200 shown in FIG. 2.

Importantly, the MAST 200 includes a TCP/IP interface 270 and internalmodule 201 allowing appropriate operational access to subscriberpresence and/or location information maintained therein. Thus, any orall external application servers 290 (e.g., chat servers, lawenforcement servers, etc.) may access subscriber presence and orlocation information regarding a wireless service provider's subscribersvia the Internet 280.

The subscriber's presence and/or location information maintained in asubscriber presence/location database 205 may be pre-configured fortransmission to various pre-set application servers 290 via the TCP/IP(i.e., non-SS7 protocol) module 201 and associated link 270.Alternatively, presence and/or location information regarding any or allsubscriber's serviced by the MAST 200 may be provided to an applicationserver 290 upon request by the application server 290.

Referring back to FIG. 2, the particular applications which can beimplemented by the various application servers 290 is virtuallylimitless. Any application which can make use of the presence and/orlocation information regarding any or all wireless subscribers(regardless of whether or not they are inside or external to aparticular wireless network) may utilize the information contained inthe database of the MAST 200 in accordance with the principles of thepresent invention.

The message flow shown in FIG. 2 relates to that of a stand-alone HLR240. The message flow utilizing an integrated HLR is shown in FIG. 3.The message flow in FIG. 2 is as follows.

A MOBILE REGISTRATION message (1.) is transmitted by a relevant wirelessdevice 1090 through the host wireless network #2 1070 to its MSC 1020.That MSC 1020 sends a MOBILE REGISTRATION NOTIFICATION (REGNOT) message(2.) to an STP 1030, which forwards a REGNOT message (3.) to the SHLR240. Up to this point the message flow is as in the conventional systemshown in FIG. 10.

However, as shown in FIG. 2, the SHLR 240 implements a message referredto herein as a registration notification forwarding mechanism (4. inFIG. 2). The registration forwarding mechanism (4.) forwards a receivedREGNOT message (3.) back out to the STP 230 as a REGNOT message (5.),destined for the MAST 200.

The STP 230 forwards the REGNOT message (5.) from the SHLR to the MAST200 using a REGNOT message (6.). Thus, the SHLR 240 shown in FIG. 2 isan otherwise conventional SHLR, but additionally includes the functionsnecessary to implement a registration notification forwarding mechanismto forward the REGNOT message (5.) to the MAST system 200 via the STP230 using another forwarded REGNOT message (6.). With the architectureof the embodiment of FIG. 2, a service provider may need to upgradesoftware running on an associated SHLR 240, but need not upgrade theirMSC 1010 or STP 230 from those otherwise conventionally available oralready installed, providing significant cost savings and efficiency.

In response to the REGNOT message (6.) received from the STP 1030, theMAST 200 updates its database 205 appropriately. The informationcontained in the database 205 is then made available as appropriate overthe TCP/IP link 270 to an external device, e.g., using an Intranet orthe Internet 280, e.g., to all requesters, to only some requesterspaying a particular fee for such a service, etc.

The service provider 250 is given operational and maintenance access tothe MAST 200 similarly to conventional access given to an SHLR, e.g.,using an X.25, RS-232 or TCP/IP link.

FIG. 3 is a detailed architecture and information flow of an embodimentof a MAST system 200 corresponding to an integrated Home LocationRegister (I-HLR) including a registration notification forwardingmechanism integrated with a mobile switching center (MSC) on a commonplatform, utilizing message flows in conformance with SS7 standards andIS-41 standards, in accordance with the principles of the presentinvention.

In particular, FIG. 3 shows that when using an I-HLR 340, thecommunications between the MSC/I-HLR common platform and the STP 330 aretypically made over an SS7 link to the common platform, and that theelements on the common platform (e.g., the MSC 310 and the I-HLR 340)may communicate with one another in proprietary ways without the need toconform to SS7 or other external signaling requirements.

The I-HLR 340 shown in FIG. 3 is an otherwise conventional I-HLR, butadditionally includes the functions necessary to implement aregistration notification forwarding mechanism to forward the REGNOTmessage (5.) to the MAST system 200 via the STP 230 using anotherforwarded REGNOT message (6.). With the architecture of the embodimentof FIG. 3, a service provider may need to upgrade software running on anassociated I-HLR 340, but need not upgrade their MSC 310 or STP 330 fromthose otherwise conventionally available or already installed.

FIG. 4 is a detailed architecture and information flow of an embodimentof a MAST system corresponding to a stand-alone Home Location Register(SHLR) including a Registration Notification copy function in asignaling transfer point (STP) and a TCP/IP connection (or SS7connection) to the MAST application, particularly useful in wirelessnetworks having HLRs which do not include a registration notificationforwarding mechanism, in accordance with the principles of the presentinvention.

In particular, FIG. 4 importantly shows an STP 430 including otherwiseconventional functions, but in addition includes a REGNOT copy andforward function.

The REGNOT copy and forward function in the STP 430 copies the REGNOTmessage (2.) received from an MSC 1020, and forwards a REGNOT copymessage (3 b.) to the MAST 200. The STP 430 also sends the otherwiseconventional REGNOT message (3.) to the SHLR 1040.

The STP 430 shown in FIG. 4 is an otherwise conventional STP, butadditionally includes the functions necessary to implement a COPY andFORWARD message to generate a copy of the REGNOT message (3.) sent tothe SHLR 1040 as a copy REGNOT message (3 b.) sent to the MAST 200. Withthe architecture of the embodiment of FIG. 4, a service provider mayneed to upgrade software running on an associated STP 430, but need notupgrade their MSC(s) 1010 or SHLR(s) 1040 from those otherwiseconventionally available or already installed.

The MAST system architecture shown in FIG. 4 has the advantage ofeliminating some communications (e.g., the registration notificationforwarding mechanism trigger (4.) and the REGNOT message (5.) shown inFIG. 3), which is particularly important because the registrationnotification forwarding mechanism trigger (4.) is an enhancedproprietary feature (i.e., not standard) to some HLRs.

The service may be provided in a provisionless mode, and all thenecessary subscriber information may reside on the HLR. Thus, there ispreferably no specific subscriber provisioning necessary on the MASTSPA. Rather, the subscriber data may be maintained at the relevant HLR.The amount of memory, e.g., random access memory (RAM) and the number ofSS7 links required by the SCP platform implementing the MAST SPA may bedetermined based on the subscriber count to be supported.

For instance, as a general guideline, consider the following example.Assuming a load of 500,000 subscribers, one (1) registrationnotification forwarding mechanism trigger per subscriber per hour, five(5) Mobile Inactivity Triggers (MITs) per subscriber per day, 1 KB ofmemory per subscriber, and an average SS7 message length of 100 octects,the number of SS7 links required in the disclosed embodiment for thisconfiguration is approximately four (4), along with approximately 500 MBof RAM.

Use of Signaling Transfer Points (STPs) between MSCs can be implementedin multiple I-HLR environments as well.

From the perspective of a wireless service provider, MAST allows theimplementation of an endless array of services and/or applications thatcan utilize presence and/or location information regarding a wirelessdevice. Specific implementations of services will depend on thecapabilities of the application servers that receive the informationfrom the MAST. For instance, knowledge of registration activity in andof itself represents a huge benefit for the service provider from amarketing perspective because it can provide additional informationregarding subscriber's habits, and general demographic data collection.

The MAST techniques and apparatus may also be used for law enforcementpurposes. For instance, data relating to mobile station activity may beused, e.g., as evidence to build a legal case against an offender.

As another benefit, subscribers of a wireless service provider can beprovided with an enhanced protection mechanism against fraud by allowingfaster detection and/or tracking of delinquent mobile devices.

Depending upon particular parameters used, other services may beimplemented. For instance, with knowledge of the location of aparticular mobile station, a wireless service provider may implement an“Emergency Location” plan. Using such a service, mobile subscribers canhave activity information (e.g., presence and/or location information,together with date and time) relating to the use of their mobile devicetransmitted to the MAST SPA in accordance with the principles of thepresent invention. The MAST SPA will log the presence and/or locationinformation regarding relevant mobile subscribers served by theassociated HRL, and pass the logged information on to any entity on theInternet or other entity or network, providing an accurate andup-to-date information source. Using the “Emergency Location” plan, thelogged location information may be used by authorities to locate aperson associated with that particular mobile device easier.

FIG. 5A is a simplified depiction of relevant parameters of a MobileRegistration Notification (REGNOT) message in conformance with SS7 andIS-41 standards utilized for determination of location information in aMAST system, in accordance with the principles of the present invention.FIG. 5B is a detailed depiction of all conventional parameters of aREGNOT message.

In particular, the REGNOT message parameters utilized by the MAST may beany or all parameters included or inferred from information within thestandard REGNOT message shown in FIG. 5B. For instance, the cell site ID502 and/or sector ID 504 of the cell servicing the relevant wirelessdevice may be used to provide a location of the wireless device, anddate and time of a communication may be used for presence information.

Other information such as power level 506 can be used to infer andfurther refine the location information. For instance, a lower powerlevel received by the wireless device 1090 (and/or higher power outputby the wireless device 1090) may be used to infer a longer distance fromthe relevant cell site receiving transmissions from the wireless device1090. Conversely, a higher power level might infer that the wirelessdevice 1090 is closer to the cell site. Thus, a sort of ‘poor man's GPS’can be provided to external entities regarding the location of asubscriber's wireless device.

FIG. 6 is a simplified depiction of relevant parameters of a MobileSubscriber Inactive message in conformance with SS7 and IS-41 standardsutilized for determination of inactive presence information in a MASTsystem, in accordance with the principles of the present invention.

In particular, a MOBILE SUBSCRIBER INACTIVE message follows the samepaths as does the REGNOT messages shown in FIGS. 2, 3 and 4. While theREGNOT message indicates an active wireless device, the receipt of aMOBILE SUBSRIBER INACTIVE message with respect to a particularsubscriber may be logged in the database 205 of the MAST 200 as presenceinformation, i.e., that the wireless device may no longer be present.

FIG. 7A is a simplified depiction of relevant parameters such aslocation in an exemplary Internet Protocol (IP) message sent from theMAST system to an application server (e.g., a Chat Server) via theInternet, in accordance with the principles of the present invention.

The particular information contained either in the database 205 of theMAST and/or which is transmitted over the TCP/IP connection 270 and theInternet 280 may depend upon the particular applications operating onany of the application servers 290. Rudimentary information may include,e.g., an IP address of the application server 290, an ID of the relevantmobile wireless device, presence information such as a date and time ofactivity, and location information either real or inferred. Realinformation may include the cell site ID and/or sector ID. Inferred orextrapolated information may include, e.g., a delta distancecorresponding to a power level of the wireless device's transmitterduring a last contact.

FIG. 7B is a simplified depiction of relevant parameters in anotherexemplary IP message such as a log of past presence and locationinformation for a particular wireless device sent from the MAST systemto an application server (e.g., a law enforcement authority) via theInternet, in accordance with the principles of the present invention.

For instance, as shown in FIG. 7B, presence and/or location informationmay be logged into a historical file for each subscriber/wirelessdevice. A particular mobile ID together with a series of databaseentries corresponding to different REGNOT commands and/or MOBILESUBSCRIBER INACTIVE messages received by the MAST can be provided to oneor more particular application servers desiring such information.

Alternatively, the presence and/or location information transmitted to adesiring application server 190 may relate to a group of subscribershaving a common attribute (e.g., most active subscribers, least activesubscribers, subscribers living in a particular region, etc.).

As disclosed, activity status information is tracked by the MAST asfollows. Initially, the MAST receives a Mobile Registration message viaa registration notification forwarding mechanism, alternatively referredto as a Registration Forward Message, from the relevant MSC/HLR (I-HLRor S-HLR), and appropriately updates the activity status in thedatabase. Upon power down of the relevant wireless device, the MAST willreceive a Mobile De-Registration message via a Mobile Inactive Trigger(MIT) from the relevant MSC/HLR, and appropriately updates the activitystatus in the database.

When a new message (e.g., a mobile registration message or mobilede-registration message) is received, the MAST application preferablyparses the message, e.g., into up to 10 parameters, and stores theparsed message portions in an appropriate MSID ordered table.

FIG. 8 shows an exemplary Mobile Station Identity (MSID) ordered tableis shown in FIG. 8.

FIG. 9 shows an exemplary process by which the parsed message portionsare processed.

In particular, as shown in step 202 of FIG. 9, the process determines ifa new REGNOT or MSINACT has been received.

If a record for the same MSID is found in the table of FIG. 8, in step204 a comparison of the status and key parameters within the two recordswill be made.

In step 208, if the status (ACT to DEACT or DEACT TO ACT) or one of thekey parameters are different from that of the previous record, a subsetof key parameters up to and including all key parameters from this newrecord will be sent to at least one, but possibly multiple IP addresseson a network.

In steps 206 and 210, the old record is replaced in the MSID table withthe new, most recent record.

The MAST receives information directly from the HLR or the STP (e.g.,I-HLR or S-HLR), which has previously validated the MSID and determinedthe need to forward the information to the MAST.

Administration of the MAST may include, e.g., configuration andmaintenance of the following:

-   -   Point-codes and Subsystem numbers of the I-HLRs that will send        information to the MAST SPA.    -   Parameters that the I-HLR will forward to the MAST SPA in the        registration notification forwarding mechanism and MIT messages.    -   Parameters that the MAST SPA will forward to the application        servers.    -   Destination IP addresses and Port numbers of the application        servers.    -   Expiration time for records that have not experienced changes        over a configurable period of time.    -   Size of the rotating log file.

There is preferably only one record per MSID in the MAST. The relevantservice provider is preferably given access to the database stored inthe MAST, e.g., through the conventional operational maintenanceprocessor (OMP).

Due to its nature, the content of this database is likely to changerapidly over time, therefore the MAST database may provide only asnapshot of the activity status of all the relevant wireless devices atany given time.

The MAST preferably keeps a temporary log of the messages sent to theapplication services in a rotating file. This rotating file may have aconfigurably fixed size, and may overwrite itself with more recentinformation, e.g., after a desired period of time determined by thelevel of message traffic. This log provides a historical representationof the activity of specific wireless devices, or groups of wirelessdevices.

Reports may be generated for the relevant service provider, e.g.,through the OMP or via a TCP/IP connection to the Internet. Possiblereports can include, e.g., various information depending upon theparameters that the relevant HLR sends to the MAST, and/or specificneeds and selections made by the particular service provider.

In case the subscriber base increases, the platform can be easily scaledto increase capacity.

Being a Wireless Intelligent Network service, MAST takes advantage ofthe improved reliability, scalability and performance of the AdvantagePlatform and the flexibility of the intelligent network approach.

Additionally, MAST is an Intelligent Network application that can beexecuted simultaneously on a single SCP platform, such as a ShortMessage Service Center, Over The Air Activation, PrePaid Wireless, etc.This fact spreads the cost of the platform over several services, thusallowing the service provider to price them in a competitive way. Froman operating standpoint, a single platform is easier to manage resultingin reduced maintenance costs.

Mobile Chat Location Register (MCLR)

The principles of the present invention may be used to implement awireless chat tracking system (i.e., Mobile Chat Location Register(MCLR)) which utilizes a change in mobile registration status toautomatically notify a chat group system outside the wireless network ofcurrent status information activity regarding a relevant device, e.g.,registration activity or inactivity timeout.

In a disclosed embodiment, a registration notification (REGNOT) messageis either explicitly forwarded or copied to an external IP basedapplication (e.g., to a mobile chat group system). The change in mobileregistration is communicated via a suitable signaling link (e.g., SS7,TCP/IP, etc.) between a Home Location Register (HLR) and the chat groupsystem. Therefore, instead of a conventionally closed system using SS7messages, REGNOT messages are pushed out over TCP/IP connections toexternal applications (e.g., chat servers) to automatically notify theexternal system of the location of a particular user.

In accordance with the principles of the present invention, a REGNOTmessage may be simply forwarded in accordance with instructions from anHLR, or all REGNOT messages received may be copied and forwarded to anexternal application, which then sifts through the copied and receivedREGNOT messages for messages of relevance to that particular externalapplication.

FIG. 12 shows an exemplary service implementation showing wireless chatstatus tracking providing an automatic on-line or off-line notificationin a chat scenario using techniques and apparatus in accordance with theprinciples of the present invention. FIG. 13 shows a more detailed blockdiagram of the SMSC 1230 shown in FIG. 12, including a REGNOT messagereceiver 1304, a REGNOT forwarder 1302, and an optional REGNOT copier1306.

For the purposes of illustration, assume that in FIGS. 12 and 13 allchat subscribers with the exception of Mobile A are alreadyparticipating in a chat session called, e.g., “Buddies”.

Scenario 1

Automatic On-Line Notification Chat Scenario in a Prepaid Environment

(1) The handset Mobile A 1202, provisioned with chat service, is poweredon or performs the IS-41 periodic or forced registration process. Thus,a Registration access message is sent from the Mobile A 1202 to theMobile Switching Center (MSC) 1204.

(2) The MSC 1204 sends the IS-41 Registration Notification (REGNOT)message to the Home Location Register (HLR) 1206.

(3) Following the authentication process of Mobile A 1202, in accordancewith the principles of the present invention, the HLR 1206 forwards theREGNOT message to, e.g., a relevant prepaid application server. This maybe performed using an IS-41 REGNOT message over an SS7 network or anequivalent registration message over a TCP/IP network.

(4) The SMSC/Prepaid service 1230 may notify a suitable wirelessInternet gateway 1210 that Mobile A 1202 is “on-line”. Such a suitablewireless Internet gateway 1210 is shown and described in co-pending U.S.application Ser. No. 09/630,762, entitled “Wireless Internet Gateway” toSmith, filed Aug. 2, 2000.

If Mobile A 1202 is a prepaid subscriber, the prepaid service may verifyan account balance for Mobile A 1202 at this point and can decide tocontinue service or not.

(5) The wireless Internet gateway 1210 forwards the REGNOT message to arelevant external chat server 1220 automatically indicating to thatexternal application that Mobile A 1202 is “on-line”.

(6) The external chat server 1220 determines that Mobile A 1202 belongsto a particular chat group, e.g., the chat group “Buddies” of thecurrent example, and automatically registers Mobile A 1202 in the chatsession.

(7) The external chat server 1220 notifies the other chat participants(e.g., the “Buddies” participants) that Mobile A 1202 is available bysending a broadcast text message to all current participants of thatchat session. At the same time, the chat server 1220 may also notifyMobile A 1202 of all current participants of that chat session.

(8) The wireless Internet gateway 1210 automatically forwards chatmessages from the chat server 1220 for delivery to the chat sessionparticipants via the relevant SMSC 1230.

(9) The short message service center (SMSC) 1230 requests the HLR 1206for short message delivery to all participating mobile subscribers.

(10) The HLR 1206 provides the SMSC 1230 with all needed information todeliver the short messages.

(11) The SMSC 1230 stores and forwards the broadcast message to the MSC1204 for delivery to the other chat participants (e.g., to Mobile B 1242and Mobile C 1252), and the list of chat participants message to theautomatically entering Mobile A 1202.

(12) The MSC 1204 delivers the chat messages to all participatingmobiles 1202, 1242, 1252.

Scenario 2

Automatic Off-Line Notification Chat Scenario in a Prepaid Environment

(1) The handset Mobile A 1202, provisioned with chat service, is poweredoff or has moved out of the relevant coverage area.

(2) The MSC 1204 detects an expiration of an inactivity timer and sendsan IS-41 Inactivity message to the Home Location Register (HLR) 1206.

(3) The HLR 1206 forwards the Inactivity message, e.g., the IS-41 MSInactivity message, over an SS7 network, or an equivalent inactivitymessage over a TCP/IP network to, e.g., a relevant prepaid applicationserver such as the SMSC/Prepaid platform 1230.

(4) The SMSC/Prepaid service 1230 notifies the wireless Internet gateway1210 that Mobile A 1202 is “off-line”.

(5) The wireless Internet gateway 1210 forwards the message to the chatserver 1220 that Mobile A 1202 is “off-line”.

(6) The external chat server 1220 determines that Mobile A 1202 belongsto, e.g., the chat group “Buddies”, and thus removes Mobile A 1202 fromthe chat session.

(7) The external chat server 1220 notifies the chat sessionparticipants, e.g., participants of the chat session “Buddies”, thatMobile A 1202 has become unavailable, by sending a broadcast textmessage to all current chat participants.

(8) The wireless Internet gateway 1210 forwards the messages fordelivery.

(9) The SMSC 1230 requests the HLR 1206 for short message delivery toall mobile subscribers.

(10) The HLR 1206 provides the SMSC 1230 with all needed information todeliver the messages.

(11) The SMSC 1230 stores and forwards the broadcast message fordelivery to Mobile wireless devices B & C, 1242 & 1252.

The MSC 1204 delivers the messages to Mobile wireless devices B & C,1242 & 1252.

Note that while the chat server 1220 shown in FIG. 12 is internal to theservice provider's network, the principles of the present inventionrelate equally to placement of the chat server 1220 external to theservice provider's network, i.e., over the Internet 1299.

This solution may be integrated with existing, commercially availableSMSC & web gateway products that enable wireless carriers & Internetservice providers (ISPs) to offer, e.g., a pre-payment billing optionfor enhanced messaging services.

The principles of the present invention have applicability for usagewith wireless intelligent network (WIN) applications, e.g., thosealready otherwise containing SMSC, prepaid, and/or web gatewayapplications. Moreover, there is applicability for usage with mobileregistration, for inactivity message forwarding to a chat server, or formobile automatic notification of subscriber status to chat server.

While the invention has been described with reference to the exemplaryembodiments thereof, those skilled in the art will be able to makevarious modifications to the described embodiments of the inventionwithout departing from the true spirit and scope of the invention.

What is claimed is:
 1. A mobile device status tracking system,comprising: a registration notification message receiver to receive aregistration notification message associated with a message subscriberdevice; and a registration notification message communicator tocommunicate, via an Internet Protocol (IP) connection, a registrationactivity status of said message subscriber device to a serviceprovider-specific application; wherein said registration notificationmessage, received at a message distribution server, notifies a group ofmessage subscriber devices of said registration activity status of saidmessage subscriber device.
 2. The mobile device status tracking systemaccording to claim 1, wherein: said service provider-specificapplication is communicated with in response to said receiving of saidregistration notification message.
 3. The mobile device status trackingsystem according to claim 1, wherein: said group of message subscriberdevices each belong to a given chat room group.
 4. The mobile devicestatus tracking system according to claim 1, wherein: said registrationnotification message communicator retains a copy of registrationnotification messages received by a mobile switching center.
 5. Themobile device status tracking system according to claim 1, furthercomprising: a wireless Internet gateway to transmit said registrationnotification message over said IP connection.
 6. The mobile devicestatus tracking system according to claim 5, further comprising: aregistration notification message handler in communication with saidwireless Internet gateway.
 7. A method of tracking a status of a mobiledevice, comprising: receiving a registration notification messageassociated with a message subscriber device; and communicating, via anInternet Protocol (IP) connection, a registration activity status ofsaid message subscriber device to a service provider-specificapplication; wherein said registration notification message, received ata message distribution server, notifies a group of message subscriberdevices of said registration activity status of said message subscriberdevice.
 8. The method of tracking a status of a mobile device accordingto claim 7, wherein: said service provider-specific application iscommunicated with in response to said receiving of said registrationnotification message.
 9. The method of tracking a status of a mobiledevice according to claim 7, wherein: said group of message subscriberdevices each belong to a given chat room group.
 10. The method oftracking a status of a mobile device according to claim 7, furthercomprising: storing a copy of registration notification messagesreceived by a mobile switching center.
 11. The method of tracking astatus of a mobile device according to claim 7, further comprising:transmitting from a wireless Internet gateway said registrationnotification message over said IP connection.
 12. The method of trackinga status of a mobile device according to claim 11, further comprising:establishing communications between a registration notification messagehandler and said wireless Internet gateway using a Signaling System #7communications protocol.
 13. A mobile device status tracking system,comprising: a status change receiver to receive a status changenotification message associated with a message subscriber device; and astatus change notification message communicator to communicate, via anInternet Protocol (IP) connection, a status change activity associatedwith said message subscriber device to a service provider-specificapplication; wherein said status change notification message, receivedat a message distribution server, notifies a group of message subscriberdevices of said status change activity of said message subscriberdevice.
 14. The mobile device status tracking system according to claim13, wherein: said service provider-specific application is communicatedwith in response to said receiving of said status change notificationmessage.
 15. The mobile device status tracking system according to claim13, wherein: said group of message subscriber devices each belong to agiven chat room group.
 16. The mobile device status tracking systemaccording to claim 13, wherein: said status change notification messagecommunicator retains a copy of status change notification messagesreceived by a mobile switching center.
 17. The mobile device statustracking system according to claim 13, further comprising: a wirelessInternet gateway to transmit said status change notification messageover said IP connection.
 18. The mobile device status tracking systemaccording to claim 17, further comprising: a registration notificationmessage handler in communication with said wireless Internet gateway.19. A method of tracking a status of a mobile device, comprising:receiving a status change notification message associated with a messagesubscriber device; and communicating, via an Internet Protocol (IP)connection, a status change activity associated with said messagesubscriber device to a service provider-specific application; whereinsaid status change notification message, received at a messagedistribution server, notifies a group of message subscriber devices ofsaid status change activity of said message subscriber device.
 20. Themethod of tracking a status of a mobile device according to claim 19,wherein: said service provider-specific application is communicated within response to said receiving of said status change notificationmessage.
 21. The method of tracking a status of a mobile deviceaccording to claim 19, wherein: said group of message subscriber deviceseach belong to a given chat room group.
 22. The method of tracking astatus of a mobile device according to claim 19, further comprising:storing a copy of status change notification messages received by amobile switching center.
 23. The method of tracking a status of a mobiledevice according to claim 19, further comprising: transmitting from awireless Internet gateway said status change notification message oversaid IP connection.
 24. The method of tracking a status of a mobiledevice according to claim 23, further comprising: establishingcommunications between a status change notification message handler andsaid wireless Internet gateway using a Signaling System #7communications protocol.